Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update packages to latest versions #179

Merged
merged 2 commits into from
Sep 7, 2024
Merged

Update packages to latest versions #179

merged 2 commits into from
Sep 7, 2024

Conversation

robford123
Copy link

Updated all packages to latest versions. Removes some vulnerabilities, especially in the Postgres libraries.

@seriouz
Copy link

seriouz commented Sep 4, 2024

Hi @robford123 why did you add

  <ItemGroup>
    <PackageReference Update="xunit.runner.visualstudio">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
    </PackageReference>
  </ItemGroup>

in many csproj?

@robford123
Copy link
Author

Upgrading the packages automatically added that in, I checked it built and tests ran ok.

@seriouz
Copy link

seriouz commented Sep 6, 2024

LoL I didn't know that Visual Studios test discovery isn't that good, so the packages is almost required when using Visual Studio.
Personally I use Rider.

@seriouz
Copy link

seriouz commented Sep 6, 2024

@robford123 Can you have a look into the merge conflicts?

@robford123
Copy link
Author

@seriouz should be all good now

@seriouz seriouz self-requested a review September 7, 2024 10:17
Copy link

@seriouz seriouz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay

@seriouz seriouz self-requested a review September 7, 2024 10:19
@seriouz seriouz merged commit 1b3790f into main Sep 7, 2024
2 checks passed
@seriouz seriouz deleted the update-packages branch September 7, 2024 10:22
@Regenhardt
Copy link

Upgrading the packages automatically added that in, I checked it built and tests ran ok.

It should actually be in the Directory.Build.props of the test directory, not sure why it was added to the individual project files again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants